chore: Add a CircleCI parameter for target publish-binary branch #32665
+88
−68
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ed value for branch - migrates trigger-publish-binary-pipeline.js to an inlined bash script to speed it up and simplify it - adds a pipeline parameter that can be set via CircleCI UI to determine which branch we use in the publish-binary pipeline, to reduce file churn and human error - updates the packages/electron/README.md to include the simplified steps
cacieprins
commented
Oct 7, 2025
| - [ ] Temporarily update the circle configuration to allow `cypress` to run against the branch | ||
| - [ ] Temporarily set target `cypress-publish-binary` branch as a `branch` property on the request body in [../../scripts/binary/trigger-publish-binary-pipeline.js](../../scripts/binary/trigger-publish-binary-pipeline.js) script, so that you can test against this branch from the electron upgrade branch. This property must be set both at the root of the body object, and on the `parameters` key. If it is not set at the root, the binary pipeline will continue to use the primary branch. | ||
| - [ ] Add your branch name to the `&full-workflow-filters` anchor in [`@pipeline.yml`](../../.circleci/src/pipeline/@pipeline.yml) |
Contributor
Author
There was a problem hiding this comment.
this can be parameterized as well (separately, to reduce delta surface)
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
cypress
|
||||||||||||||||||||||||||||||||||||||||
| Project |
cypress
|
| Branch Review |
ci/parameterize-binary-branch
|
| Run status |
|
| Run duration | 19m 12s |
| Commit |
|
| Committer | Cacie Prins |
| View all properties for this run ↗︎ | |
| Test results | |
|---|---|
Failures
|
0
|
Flaky
|
9
|
Pending
|
1098
|
Skipped
|
4
|
Passing
|
26530
|
| View all changes introduced in this branch ↗︎ | |
Warning
Partial Report: The results for the Application Quality reports may be incomplete.
UI Coverage
45.74%
|
|
|---|---|
|
Untested elements
|
186
|
|
Tested elements
|
161
|
Accessibility
97.98%
|
|
|---|---|
|
Failed rules
|
4 critical
8 serious
2 moderate
2 minor
|
|
Failed elements
|
101
|
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
cacieprins
force-pushed
the
ci/parameterize-binary-branch
branch
from
57afea5 to
5d50a15
Compare
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Member
jennifer-shehane
left a comment
jennifer-shehane
left a comment
There was a problem hiding this comment.
@cacieprins Is it possible to have the trigger-publish-binary-pipeline workflow run on this PR to test it working?
jennifer-shehane
approved these changes
Oct 30, 2025
AtofStryker
approved these changes
Oct 31, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Additional details
This should reduce cognitive load regarding branches when performing Electron upgrades.
Steps to test
How has the user experience changed?
PR Tasks
cypress-documentation?type definitions?Note
Adds a CircleCI parameter to choose the publish-binary target branch and replaces the Node trigger script with a new bash-based CircleCI command, updating docs accordingly.
publish-binary-branchto/.circleci/config.ymland.circleci/src/pipeline/@pipeline.yml.commands/trigger-publish-binary-pipeline.yml(bash) that triggers thecypress-publish-binarypipeline, outputs~/triggered_pipeline.json, and acceptstarget-repo-branch.create-and-trigger-packaging-artifactsto calltrigger-publish-binary-pipelinewithtarget-repo-branch: << pipeline.parameters.publish-binary-branch >>.scripts/binary/trigger-publish-binary-pipeline.js.packages/electron/README.mdto use the new Circle parameterized flow (add branch to&full-workflow-filters, setpublish-binary-branchin CircleCI UI); remove references to the old JS trigger script.Written by Cursor Bugbot for commit 8529c13. This will update automatically on new commits. Configure here.